Apparatus and method for charging an electric device using a label

ABSTRACT

In a method for charging an electric device by a service rendering system, a controller of the service rendering system receives an image captured by an image sensor and processes the image to identify a label in the image as corresponding to the electric device. The controller obtains a service point location encoded in the label, where the service point location includes a location relative to a location of the label. The controller obtains service information included in the label, where the service request includes a charging service, and the charging service includes a description of an electric charging input of the electric device. The controller calculates a label position of the label using the image of the label and calculates a service point position using the service point location and the label position, where the service point position includes the electric charging input.

BACKGROUND OF THE INVENTION Field

This invention relates generally to the charging of an electric deviceusing, a label, and more specifically, to a service rendering systemequipped with an image sensor controller for rendering a chargingservice according to information on a service label image captured bythe image sensor.

Related Art

Many optical cameras, either RGB cameras or night vision cameras arecapable of capturing high quality images. Mounting the cameras onto aservice rendering machine allows the service rendering machine toautonomously recognize the object requesting the service throughprocessing a captured image of the object. For example, industrialrobotic arms equipped with cameras are capable of performing repairs,putting on screws, assembling, and other mechanical procedures onto theobject.

These robotic arms are typically stationary, and the objects need to betransported to be near the robotic arms or to a pre-determined positionwhere the robotic arms can service the objects. These robotic arms arenot equipped to work in a wider or open area where the robotic armswould be required to move to the objects in order to service theobjects.

For example, in a shopping mall, the mall owner may want a securitycheck to be conducted after the mall is closed. The security check mayinclude: locking doors; backing up surveillance cameras' video footage;charging security sensors and capturing data backup; emptying or fillingcontainers such as garbage bins, hand sanitizers, and soap dispensers;charging electronic devices; and servicing other electronic ormechanical devices before the mall opens again. Typically, the mallowner hires custodians to perform the tasks. However, many devices andgadgets, such as cameras and sensors, are installed in hard to reachplaces. Special services need to be scheduled for technical crew toservice these exceptional devices and gadgets. It would be moreeffective and efficient for the mall owner to deploy an autonomousservice rendering vehicle to reach and service all objects.

In another scenario on a university campus, the school may want toinstall, security devices (e.g., smart light poles, security cameras andsensors, and smart door locks) throughout the campus, cost-efficientautonomous delivery and utility vehicles or carts, smart landscape withsensors, and/or smart solar panels and other smart devices and sensors.These smart electronic computing devices and vehicles require regularmaintenance such as electric charging, re-calibration, adjustments, datadownload, material refill, cleaning, content removing, or componentreplacement, etc. These devices are likely installed in small areas,high location, hard to reach places, or in places beyond reach of humantechnicians but requiring special accessing tools. It is desirable andnecessary for the devices to be serviced by an autonomous servicerendering vehicle that can locate and reach these devices.

In one scenario in an airport, a number of mobile service and vendingkiosks may be deployed throughout the airport. These kiosks may beautonomous and move from one location to another location from time totime. The airport may wish for the kiosk battery cells replaced fromtime to time at their current location instead of moving the kiosks backto their charging stations. It is therefore desirable for an autonomousservice rendering vehicle to locate and service the kiosks. The servicerendering vehicle can replace or recharge the battery cells, refillproducts within the kiosks, repair, replace or update hardware andsoftware components of the kiosks.

In order to perform the services above, the service rendering vehiclerequires a precise position of a service point in order to move to aservice object and to render the service on a service object.

BRIEF SUMMARY OF THE INVENTION

Disclosed herein is a method for rendering a charging service by aservice rendering system and a corresponding apparatus and a computerreadable medium as specified in the independent claims. Embodiments ofthe present invention are given in the dependent claims. Embodiments ofthe present invention can be freely combined with each other if they arenot mutually exclusive.

According, to one embodiment of the present invention, in a method forcharging an electric device by a service rendering system, a controllerof the service rendering system: receives an image captured by an imagesensor; processes the image to identify a label in the image ascorresponding to the electric device; obtains a service point locationencoded in the label, where the service point location includes alocation relative to a location of the label; obtains serviceinformation included in the label, where the service request includes acharging service, and the charging service includes a description of anelectric charging input of the electric device; calculates a labelposition of the label using the image of the label; and calculates aservice point position using the service point location and the labelposition, where the service point position includes the electriccharging input.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE FIGURES

FIG. 1 illustrates an exemplary embodiment of a system of using aservice rendering vehicle to autonomously render a service at a servicepoint based on a service label.

FIG. 2 illustrates an embodiment of a service computing device,

FIG. 3 illustrates an exemplary embodiment of a process to calculate aposition of a service label from a service rendering vehicle.

FIG. 4 illustrates an exemplary embodiment of a process to calculate aposition of a service point from a service, rendering vehicle.

FIG. 5 illustrates an exemplary embodiment of a service request.

FIG. 6 illustrates an exemplary embodiment of an authentication processimplemented at a service point.

FIG. 7 illustrates an exemplary embodiment of a process, to render aservice to a lock.

FIG. 8 illustrates an exemplary embodiment of a process to render aservice to a sensor.

FIG. 9 illustrates an exemplary embodiment of a process to render abattery charging service.

FIG. 10 illustrates an exemplary embodiment of a process to render aservice to a container.

FIG. 11 illustrates an exemplary embodiment of a process to render adynamic computing service.

DETAILED DESCRIPTION OF THE INVENTION

The following description is presented to enable one of ordinary skillin the art to make and use the present invention and is provided in thecontext of a patent application and its requirements. Variousmodifications to the embodiment will be readily apparent to thoseskilled in the art and the generic principles herein may be applied toother embodiments. Thus, the present invention is not intended to belimited to the embodiment shown but is to be accorded the widest scopeconsistent with the principles and features described herein.

Reference in this specification to “one embodiment”, “an embodiment”,“an exemplary embodiment”, or “a preferred embodiment” means that aparticular feature, structure, or characteristic described in connectionwith the embodiment is included in at least one embodiment of theinvention. The appearances of the phrase “in one embodiment” in variousplaces in the specification are not necessarily all referring to thesame embodiment, nor are separate or alternative embodiments mutuallyexclusive of other embodiments. Moreover, various features are describedwhich may be exhibited by some embodiments and not by others. Similarly,various requirements are described which may be requirements for someembodiments but not other embodiments. In general, features described inone embodiment might be suitable for use in other embodiments as wouldbe apparent to those skilled in the art.

FIG. 1 illustrates an exemplary embodiment of a system of using aservice rendering vehicle to autonomously render a service at a servicepoint based on a service label. In one embodiment, a service renderingvehicle 601 services a service object 360. Service rendering vehicle 601may navigate in an area to locate service object 360 and render one ormore services to service object 360. In one embodiment, servicerendering vehicle 601 navigates in a shopping mall, a strip mall, anoffice, a business park, a building, a campus, an apartment, a residencehome, a multi-tenant building, an airport or an area where serviceobject 360 is to be found, and renders the service requested by aservice request 357 for service object 360 at service point 361. In oneembodiment, service rendering vehicle 601 identifies service object 360via a service label 350, typically placed at a location near the serviceobject 360. In one embodiment, service label 350 is a label posted on awall, a window, a door or a pole near service object 360, or directlyonto service object 360. In one embodiment, service rendering vehicle601 includes a camera 331 taking, a picture or an image 341 of an areathat includes service label 350. Service rendering vehicle 601identifies service label 360 using a label image 343 of service label350 shown in the image 341. In one embodiment, service rendering vehicle601 uses label image 343 to identify service label 350 and obtainsinformation embedded within service label 350. In one embodiment,service label 350 includes label information such as label physicaldimension 351, service point location 353 and service request 357. Inone embodiment, the label information is encoded as a code, a number, ora piece of text into service label 350. In one embodiment, service label350 encodes a network link such as a URL where the label information maybe obtained. In one embodiment, service label 350 directly encodes partof the label information and a network link where the remainder of thelabel information may be obtained.

In one embodiment, service rendering vehicle 601 identifies servicelabel 350 and obtains label physical, dimension 351, service pointlocation 353 and service request 357 from the service label 350. In oneembodiment, service rendering vehicle 601 includes a processingcontroller 310, which uses the label physical dimension 351, image 341,label image 343, and attributes of camera 331 to calculate a labelposition 381 of service label 350. The calculated label position 381indicates a position of service label 350 away from service renderingvehicle 601. In one embodiment, service rendering vehicle 601 includes aservicing arm 333 which can render services to service object 360. Labelposition 381 is calculated to be a relative position from arm 333. Uponcalculating label position 381, controller 310 combines label position381 and service point location 353, which indicates a location ofservice point 361 for service object 360, and to calculate a servicepoint position 383 indicating a location of service point 361 relativeto the location of the service rendering vehicle 601. In one embodiment,service point position 383 is calculated in, relation to the location ofthe service rendering vehicle 601 and/or the arm 333.

In one embodiment, controller 310 instructs service rendering vehicle601 and/or the arm 333 to navigate autonomously (i.e., without userintervention) towards service point position 383. In one embodiment,controller 310 instructs service rendering vehicle 601 to move, suchthat the service rendering vehicle 601 is in close proximity to theservice point position 383, and then the controller 310 instructs thearm 333 to move to the service point position 383. In one embodiment,controller 310 instructs arm 333 to, render one or more services atservice point 361 of service object 360 according to informationobtained from service request 357. In one embodiment, service request357 includes information related to one or more of an authenticationprocess, a data communication session, a wireless connectioninstruction, a physical operation, a lock (de)-activation instruction, asensor command, a data download or retrieval instruction, a physicalcontainer or tray service instruction, a battery charging instruction,or other services to be rendered at service point 361. In oneembodiment, service request 357 includes or encodes a plurality ofcomputing instructions, and controller 310 executes the plurality ofcomputing instructions in service request 357 in order to render therequested service.

In one embodiment, service rendering vehicle 601 includes materials 330which may contain a data storage (not shown), which stores data forservice request 357, a battery cell, a tray or container, a basket, ormaterials to fill service object 360.

FIG. 2 illustrates an exemplary embodiment of hardware components of aservice computing, device which can be used for a service renderingvehicle, a controller or to house a controller. In one embodiment,service computing device 510 is a computing device including a processormodule 511, an output module 515, an input module 517, and a storage519. In one embodiment, computing device 510 may include a networkmodule 513 or a clock 514. In one embodiment, processor module 511includes one or more general processors, a multi-core processor, anapplication specific integrated circuit based processor, a system on achip (SOC) processor or an embedded processor. In one embodiment, outputmodule 515 includes or connects to a display for displaying videosignals, images and text, and an audio speaker to play sound signals. Inone embodiment, output module 515 includes a data interface such as USB,HDMI, DVI, DisplayPort, thunderbolt or a wire-cable connecting to adisplay or a speaker. In one embodiment, output module 515 connects to adisplay or a speaker using a wireless connection or a wireless datanetwork. In one embodiment, input module 517 includes a physical orlogical keyboard, buttons, keys, or microphones. In one embodiment,input module 517 includes or connects to one or more image sensor 516such as a camera sensor, an optical sensor, a night-vision sensor, aninfrared (IR) sensor, a motion sensor, a direction sensor, a proximitysensor, a gesture sensor, or other sensors that is usable to provide aninput image to service computing device 510. In one embodiment, inputmodule 517 includes a physical panel housing one or more sensors. In oneembodiment, storage 519 includes a storage medium, a main memory, a harddisk drive (HDD), a solid state drive (SSD), a memory card, a ROMmodule, a RAM module, a USB disk, a storage compartment, a data storagecomponent or other storage component. In one embodiment, network module513 includes hardware and software to connect to a wireless data networksuch as a cellular network, a mobile network, a Bluetooth network, anNFC network, a personal area network (PAN), a WiFi network, or a LiFinetwork. In one embodiment, network module 513 connects to data networksuch as Internet, private data network, campus network, data centernetwork, Ethernet network, home network, local area network, or ahotspot data network. Storage 519 includes executable instructions whenread and executed by the processor module 511 of computing device 510implement one or more functionalities of the current invention.

In one embodiment, service computing device 510 includes a mechanicalarm 518 which may include one or joints that can be rotated, moved,extended, or retracted. In one embodiment, mechanical arm 518 isprogrammable and controlled by processor module 511 through one or moreprogrammable instructions stored in storage 519. In one embodiment,mechanical arm 518 houses a hardware component of network module 513such as an antenna, or a connector, allowing network module 513 toconnect wirelessly or physically using mechanic arm 518. In oneembodiment, mechanical arm 518 houses one or more sensors such asinfrared sensors, temperature sensor, moisture sensor, smoke detector,sound or ultrasound microphone, or other sensors. In one embodiment,mechanical arm 518 houses one or more sprays or signal emitters such asnear-infrared emitter, light emitter, sound and ultrasound speaker,heater, water/moisture spray, or air spray.

In one embodiment, service computing device 510 includes a navigationmodule 512 which may include one or more wheels, one or more legs, oneor more air propellers, one or more rotor blades, or other hardwarecomponents allowing service computing device 510 to move, run, hover,fly, swim, elevate, or climb. In one embodiment service computing device510 includes autonomous driving and navigation capabilities allowingservice computing device to move from one location to another locationwithout user intervention.

In one embodiment, service computing device 510 includes a clock 514,which provides date and time information to computing device 510.

In one embodiment, service computing device 510 does not include all themodules. In one embodiment, computing device 510 does not have networkmodule 513, locomotive module 512, or clock 514.

Returning to FIG. 1 , service rendering vehicle 601 is a servicecomputing device 510. In one embodiment, controller 310 includes acomputing device housed in service computing device 510. In oneembodiment, service rendering vehicle 601 is a small vehicle deployed ina building to service facilities within the building. In one embodiment,service rending vehicle 601 is deployed in a shopping mall or shoppingarea to service stores and shops, such as to lock doors, to electricallycharge digital locks, to download security surveillance camera imagesand videos, to change security locks, to replace batteries, to checkwhether stores are being occupied using infrared sensors, to detectsmoke or fire, to survey pressure, temperature or humidity. In oneembodiment service rendering vehicle 601 can be deployed under water toservice valves and other underwater facilities. In one embodiment,service rendering vehicle 601 can be deployed to service facilitiesalong a pole, a tall wall or a building structure.

In one embodiment, arm 333 is a mechanical arm. In one embodiment, arm333 is a programmable mechanical arm that can be programmed to move toservice point position 383.

In one embodiment, materials 330 includes a data storage used to servicethe service object 360. The data storage may store data and a pluralityof programming instructions. In one embodiment materials 330 include ahardware storage to house one or more containers or trays. In oneembodiment, materials 330 includes one or more packages of fluid, fuel,battery cells, or other physical materials for servicing service object360.

In one embodiment, service label 350 is a physical label which mayinclude a code such as a bar code, a QR code, a 2-dimensional bar code,a 3-dimensional bar code, a pattern, a colored pattern, ablack-and-white pattern, a colored blob, a sequence of one or morecharacters, a product code, a serial number, or a textual description,or an image recognizable by controller 310. In one embodiment, servicelabel 350 includes a display, connected to a computing device, which maybe a color display or an e-paper display. The display displays a labelwhich may include a bar code, a QR code, a 2-dimensional bar code, a3-dimensional bar code, a pattern, a colored pattern, a black-and-whitepattern, a colored blob, a sequence of one or more characters, a productcode, a serial number, or a textual description, or an imagerecognizable by controller 310.

In one embodiment, service label 350 includes a code indicating a labelphysical dimension 351 of service label 350, indicating a real-worldsize of service label 350. In one embodiment, label physical dimension351 includes one or more of a length, a height, a width, a diagonallength of service label 350. For example, label physical dimension 351indicates a length of 1 inch, 18 inches, 1.2 cm, 200 cm or 20 mm, adimension of 1-inch×0.75 inch, 15 inches×8 inches, 2 cm×1.5 cm, or adiagonal length of 5 inches or 40 inches. In one embodiment, controller310 uses service label 350 code to obtain label physical dimension 351by querying another computing device, such as a network computer over adata network. In one embodiment, controller 310 obtains label physicaldimension 351 through matching the service label 350 code to a labelphysical dimension 351 stored in a table in a storage module connectedto controller 310. In one embodiment, service label 350 code may,include a serial number, a product, code, product or service identity abar code, a QR-code, a piece of text, a string of alpha numericcharacters, a pixel pattern or a printed code, a serial number, or apart number. For example, label physical dimension 351 includes an alphanumeric string that includes “dimension: 2-inch-wide”, “2 cm×2 cm”, “1.2cm×2.5 cm”, “D:mm:3:4” to indicate the dimension is 3 mm×4 mm, or“diagonal 3 in” to indicate a diagonal dimension of 3 inches.

In one embodiment, service object 360 includes a physical object such asa key lock, a digital lock, a sensor, a camera, a container, a handsanitizer bottle, a pill dispenser, a valve, a thermostat, a smokedetector, a tray, a food tray, a basket, a bin, a door, an electricappliance, a computing device, an electronic gadget, a robot, anautonomous vehicle, or a serviceable object typically found in a store,a restaurant, a resident, a building, a hospital, a commercial building,a warehouse, an apartment, a business park, a water pool, or a campus.

In one embodiment, service point 361 corresponds to a location of aservice object 360 component to be serviced. In one embodiment, servicepoint 361 includes an antenna, a physical connector, a networkingconnector, an electric charging input connector, an electric chargingpad, a servicing pad, a slide holding a container, a fill hole, a turnwheel, a latch, a wireless service point or a physical service point forservice object 360.

FIG. 3 illustrates an exemplary embodiment of a process to calculate aposition of a service label from a service rendering vehicle. In oneembodiment, camera 331 captures image 341 which includes label image343. In one embodiment, controller 310 instructs camera 331 to captureimage 341. In one embodiment, controller 310 obtains image 341 fromcamera 331. Controller 310 examines image 341 and identifies the labelimage 343 shown in image 341 as a service label 350. In one embodimentcontroller 310 determines that the label image 343 includes one or moreof a QR code, a bar code, a piece of text, a color code, and a coloredshape. The controller 310 identifies the label image 343 as a servicelabel 350 by determining that the code, shape or text indicates aservice label 350. In one embodiment, the code, text or colored shape ofservice label 350 includes a service request 357, a service pointlocation 353, and/or a label physical dimension 351 which specifies aphysical size or dimension of service label 350 (see also FIG. 1 ).Label physical dimension 351 may be 1 inch by 1 inch, 3 cm by 5 cm, 1 cmby 7 cm, 10 inches by 8 inches, or a physical dimension measured byunits of length in width and height. In one embodiment, label physicaldimension 351 includes a dimension identity which controller 310 uses tolook up a physical dimension using the dimension identity and apre-stored dimension table, or using the dimension identity to query anetwork computer over a data network.

In one embodiment, controller 310 calculates the label image dimension347 of label image 343. In one embodiment, label image dimension 347 maybe 120 pixels by 120 pixels, 100 pixels by 500 pixels, 50 pixels by 50pixels, 1000 pixels by 1000 pixels, or the width and height measuredwith the image length as one unit. In one embodiment, controller 310calculates a label image position 345 of label image 343 within image341. In one embodiment, label image position 345 is calculated as animage position from the center of image 341, top left corner of image341 bottom right corner of image 341 or any reference point in image341.

In one embodiment, controller 310 determines an image dimension 342 ofimage 341. Image dimension 342 may be 3000 pixels by 4000 pixels, 4500pixels by 4500 pixels, 2000 pixels by 8000 pixels or any image dimensionaccording to a property of camera 331. In one embodiment, controller 310obtains image dimension 342 from an attribute of camera 331. In oneembodiment, controller 310 specifies image dimension 342 when controller310 instructs camera 331 to capture image 341.

In one embodiment, camera 331 is associated with a focal length 332attribute corresponding to one or more optical lens of camera 331, andwith an image sensor dimension 334 attribute corresponding to an area ofan image sensor of camera 331. In one embodiment, focal length 332 maybe 35 mm, 29.7 mm, 26 mm, or a focal length value published by themanufacture of camera 331. In one embodiment, image sensor dimension 334may be 17 mm{circumflex over ( )}2 in 4:3 mode, 4.2 mm×5.6 mm, or avalue published by the manufacture of camera 331. In one embodiment,image sensor dimension 334 is calculated by controller 310 using a pixelsize attribute of camera 331. In one embodiment, controller 310 obtainsor calculates focal length 332, image sensor dimension 334 and imagedimension 342 based on stored camera 331 attributes. In one embodiment,controller 310 calculates distance index 335 using focal length 332,image dimension 342 and image sensor dimension 334 using the followingequation (1)A=B*(C/D)  (1)where,

A=distance index 335

B=image dimension 342

C=focal length 332

D=image sensor dimension 334.

In one embodiment, controller 310 uses the width dimensions of imagedimension 342 and image sensor dimension 334 to calculate distance index335. In one embodiment, controller 310 uses the height dimensions ofimage dimension 342 and image sensor dimension 334 to calculate distanceindex 335.

In one embodiment, distance index 335 is an attribute of camera 331 andcontroller 310 obtains distance index 334 from camera 331 attributerecord.

In one embodiment, controller 310 calculates label position 381 based onlabel physical dimension 351, distance index 335 and label imageposition 345. Controller 310 calculates label position 381 distance as adistance away, from the location of camera 331 or from the location ofthe service rendering vehicle 601 using equation (2), where controller310 may use the widths of label image dimension 347 and label physicaldimension 351, or the heights of label image dimension 347 and labelphysical dimension 351.Ed=A*(F/G)  (2)where,

Ed=label position 381 distance

A=distance index 335

F=label physical dimension 351

G=label image dimension 347.

Controller 310 calculates label position 381 x-position relative to anx-position of the camera 331 location or from service rendering vehicle601 location using equation (3)Ex=Hx*(Fw/Gw)  (3)where,

Ex=label position 381 x-position

Hx=label, image position 345 x-position

Fw=label physical dimension 351 width

Gw=label image dimension 347 width

Controller 310 calculates label position 381 v-position relative toy-position of camera 331 location or from service rendering vehicle 601location using equation (4)Ey=Hy*(Fh/Gh)  (4)where,

Ey=label position 381 y-position

Hy=label image position 345 y-position

Fh=label physical dimension 351 height

Gh=label image dimension 347 height

In one embodiment, label position 381 is calculated to be a coordinate(Ex, Ey, Ed) according to equations (2)-(4), where service label 350 isof Ex in horizontal distance, Ey in vertical distance and Ed, in a depthrelative to a camera 331 location or service rending vehicle 601location.

FIG. 4 illustrates an exemplary embodiment of a process to calculate aposition of a service point from a service rendering vehicle. In oneembodiment, controller 310 processes label image 343 for service label350 to further obtain a service point location 353. In one embodiment,service label 350 includes a code or a piece of text indicating servicepoint location 353. In one embodiment, service point location 353includes a coordinate of length units showing a x-dimension, ay-dimension and a depth, where the coordinate indicates the location ofservice point 361 relative to the location of the service label 350. Inone embodiment, service point location 353 includes a coordinate (10inches, 8 inches, 0 inches) indicating service point 361 is 10 inches onthe right of, 8 inches below and same depth as service label 350. In oneembodiment, service point location 353 includes a coordinate (−4 inches,3 inches, 1 inch) indicating service point 361 is 4 inches on the leftof, 3 inches above and 1 inch deep from service label 360. In oneembodiment, controller 310 identifies the service point location 353from label image 343 and extracts the coordinate from the service pointlocation 353. Controller 310 calculates a service point position 383using service point location 353 and a label position 381 calculated asdescribed above with reference to FIG. 3 . In one embodiment, servicepoint position 383 includes a coordinate (Fx, Fy, Fd) where Fx is aservice point position 383 x-position, Fy is a service point position383 y-position and Fd is a service point position 383 distance. Servicepoint position 383 is calculated to be a position relative to theposition of the service rendering vehicle 601.

In one embodiment, service point location 353 includes a coordinate(SPLx, SPLy, SPLd) indicating a x-position SPLx, a y-position SPLy, ad-depth SPLd of service point 361 of service object 360 from servicelabel 350. (Fx, Fy, Fd) of service point position 383 is calculatedusing the following equations:Fx=Ex+SPLx  (5)Fy=Ey+SPLy  (6)Fd=Ed+SPLd  (7)where (Ex, Ey, Ed) is a coordinate corresponding to label position 381,described above with reference to FIG. 3 . Thus, service point position383 coordinate (Fx, Fy, Fd) represents a position relative to theposition of the service rendering vehicle 601. More specifically, thecoordinate (Fx, Fy, Fd) represents a position relative to the positionof the controller 310, the arm 333, the camera 331, or some othercomponent of the service rendering vehicle 601.

FIG. 5 illustrates an exemplary embodiment of a service request. In oneembodiment, service label 350 includes a code for a service request 357.Service request 357 includes one or more pieces of information such asconnection information 371, authentication information 373, and serviceinformation 370, The service information 370 may include one or more ofthe following: lock service 375; sensor service 376; charging service377; container service 378; and computing service 379. In oneembodiment, connection information 371 includes information about aconnection to be established with the service object 360 at servicepoint 361. In one embodiment, connection information 371 providesinformation allowing service rendering vehicle 601 to establish a dataconnection with service object 360. In one embodiment, connectioninformation 371 includes wireless connection information such as use ofradio frequency (RF), LiFi, WiFi, 802.11, NFC, 802.15, Personal AreaNetwork (PAN), Bluetooth, SSW, wireless identity, password, passcode,security key, link-layer protocol, signal proximity radius, or a channelnumber or frequency. In one embodiment, connection information 371includes physical connection information such as use of Ethernet, serialport, USB connection, or other physical connector information,link-layer protocol, link-layer attributes such as VLAN, security key,passcode or other physical connection information.

In one embodiment, authentication information 373 provides an indicationof whether authentication of the service rendering vehicle 601 isnecessary to access service object 360, and if so, further includesinformation for the authentication process. In one embodiment,authentication information 373 includes a method of authentication, anauthentication challenge, a question, or a request for an, identity,security key, or a password.

In one embodiment, lock service 375 indicates service object 360includes a lock and an operation service request to operate on the lock.In one embodiment, service object 360 includes a digital lock, aphysical lock, an eye-scanner lock, a remote controlled lock, or anylock that can be operated by service rendering vehicle 601. In oneembodiment lock service 375 includes a locking operation, an unlockingoperation, a lock configuration operation, a lock access event logtransfer operation, or other lock operational service. In oneembodiment, lock service 375 includes one or more instructions toperform the requested lock operation.

In one embodiment, sensor service 376 indicates service object 360includes a sensor and an operation service request to operate on thesensor. In one embodiment, sensor service 376 includes an operationrequest to activate, de-activate, calibrate, adjust, or configure thesensor of service object 360. In one embodiment, sensor service 376includes instructions to connect to the sensor of service object 360 atservice point 361. In one embodiment, the sensor is a remote controlledsensor, and sensor service 376 includes wireless connectioninstructions, which may be described in connection information 371. Inone embodiment, service object 360 includes a data storage for storingdata captured by the sensor. Sensor service 376 includes a data transferrequest to transfer the captured data to service rendering vehicle 601.In one embodiment, sensor service 376 includes a data transfer requestto transfer data from service rendering vehicle 601 to the sensor ofservice object 360.

In one embodiment, service object 360 includes an electronic device, andcharging service 377 includes a service request to electrically chargethe electronic device via service point 361. In one embodiment, servicepoint 361 includes an electric charging input and charging service 377includes a description of the electric charging input. In oneembodiment, service point 361 includes a wireless electric charging areaand charging service 377 describes the wireless charging requirement. Inone embodiment, service object 360 includes a field replaceable orswappable battery cell located at service point 361, and chargingservice 377 describes the battery cell.

In one embodiment, container service 378 indicates service object 360includes a physical container. Container service 378 includes a servicerequest to service the container. In one embodiment, container service378 includes an operation service to empty the container, to fill thecontainer with material, to remove the container and put it into servicerendering vehicle 601, to place a container from service renderingvehicle 601 onto service point 361, to swap out the container withanother container in service rendering vehicle 601, or to place an itemfrom service rendering vehicle 601 onto the container.

In one embodiment, service request 357 includes a computing service 379.In one embodiment, computing service 379 describes a computingprogramming service and includes one or more computing programminginstructions to be executed by service rendering vehicle 601. In oneembodiment, computing service 379 includes a detailed description ofservice object 360, service point 361, and one or more instructions toservice the service object 360.

FIG. 6 illustrates an exemplary embodiment of an authentication processat a service point. In one embodiment, controller 310 processes servicepoint position 383, as described above with reference to FIG. 4 , andissues instructions to service rendering vehicle 601 to move to servicepoint 361. In one embodiment, controller 310 instructs service renderingvehicle 601 to move arm 333 to service point 361. In one embodiment,service rendering vehicle 601 moves towards service point 361 accordingto service point position 383. When service rendering vehicle 601determines it is close to service point 361, service rendering vehicle601 moves arm 333 to service point 361.

In one embodiment, controller 310 processes connection information 371to connect to service object 360 via service point 361. In oneembodiment, connection information 371 indicates a wireless connectionand a proximity distance from which a wireless connection can be made.Controller 310 instructs service rendering vehicle 601 to move withinthe proximity distance 610 of the service point 361. In one embodiment,service rendering vehicle 601 moves itself or the arm 333 within thearea, where the proximity distance 610 is defined as a radius aroundservice point 361. The service rendering, vehicle 601 informs controller310 when it has arrived within the proximity distance 610. Upon beinginformed that service rendering vehicle 601 is within the proximitydistance 610, controller 310 connects to service object 360 using thewireless connection information 371. In one embodiment, controller 310obtains connection security data 391, pre-stored in controller 310 orservice rendering vehicle 601, and uses connection security data 391 toconnect to service object 360. In one embodiment, connection securitydata 391 includes a security key, a passcode, a pin code, an, answer toa question, or an authorized code. In one embodiment, controller 310obtains connection security data 391 from a network computer. Controller310 may use connection information 371 to obtain connection securitydata 391 from the network computer.

In one embodiment, connection information 371 indicates a physicalconnection. Controller 310 instructs service rendering vehicle 601 to,move arm 333 to service point 361 and to connect or attach arm 333directly onto service point 361. Upon knowing the attachment iscompleted from service rendering vehicle 601, controller 310 issuescommands or signals via the physical connection at service point 361, inorder to connect to service object 360. In one embodiment, controller310 issues the commands and signals according to connection, information371 and obtained connection security data 391.

In one embodiment, upon establishing a connection to service object 360,controller 310 processes authentication information 373 to perform anauthentication process with the service object 360. In one embodiment,controller 310 retrieves authentication security data 393, eitherobtained from a network computing device or pre-stored in controller 310or service rendering vehicle 601. Controller 310 uses authenticationsecurity data 393 to respond to one or more authentication query fromservice object 360.

In one embodiment, controller 310 determines it is authenticated byservice object 360. Controller 310 proceeds to service the serviceobject 360.

FIG. 7 illustrates an exemplary embodiment process to render a serviceto a lock. In one embodiment controller 310 processes lock service 375which indicates service object 360 includes a lock 395. In oneembodiment, lock service 375 indicates lock 395 is a wireless remotecontrolled lock. Lock service 375 may include wireless connectioninformation of lock 395 or a reference to connection information 371 fora wireless connection to lock 395. The controller 310 instructs theservice rendering vehicle 601 to move within the proximity distance 610.Upon being informed that the service rendering vehicle 601 have movedwithin the proximity distance 610, the controller 310 establishes awireless connection to lock 395 according to the wireless connectioninformation of lock 395 or connection information 371.

In one embodiment, lock 395 is a key lock, requiring a physicalconnection at service point 361 in order to be operated. Lock service375 includes the physical connection information or a reference toconnection information 371 for the physical connection information toattach at service point 361. Controller 310 instructs service renderingvehicle 601 to attach physically at service point 361.

In one embodiment, lock service 375 includes a lock operation.Controller 310 retrieves lock operation data 335 from materials 330corresponding to the lock operation included in lock service 375. In oneembodiment, lock service 375 includes a brand name, a manufactureridentity, a make, a model number, a serial number or an identity of lock395. Controller 310 uses lock service 375 to retrieve lock operationdata 335, which may include a data connection protocol, a piece ofsecurity data or key code to operate lock 395, an operation sequence orinstructions, corresponding to the brand, manufacturer, make, modelnumber, serial number or lock identity. In one embodiment, lock service375 includes one or more lock operations such as to activate,de-activate, lock, unlock, arm, disarm, configure a key code, reset.Lock operation data 335 includes instructions and key-code for the lockservice 375. In one embodiment, lock operation data 335 includesinstructions to turn arm 333, to issue data signals, to generateelectronic pulses, or other mechanical, data communication, orelectronic instructions. In one embodiment, lock operation data 335includes a key code to lock, unlock, activate, de-activate, arm ordisarm lock 395.

In one embodiment, lock 395 includes a data store storing data used orcaptured by lock 395. The captured data may include event log entries,usage data, configuration data, networking data, key code, securitydata, or other data relevant to lock 395. In one embodiment, lockservice 375 includes a data transfer operation to upload lock 395 dataor to download lock 395 data. Controller 310 processes lock service 375and transfers lock 395 to store into lock operation data 335, or sendslock operation data 335 to lock 395 to be stored, according to lockservice 375.

FIG. 8 illustrates an exemplary embodiment of a process to render aservice to a sensor. In one embodiment, controller 310 processes sensorservice 376 which indicates service object 360 includes a sensor 396. Inone embodiment, sensor service 376 indicates sensor 396 is wirelesslycontrolled. Sensor service 376 may include wireless connectioninformation of sensor 396 or a reference to connection information 371for a wireless connection to sensor 396. The controller 310 instructsthe service rendering vehicle 601 to move within the proximity distance610. Upon being informed that the service rendering vehicle 601 havemoved within the proximity distance 610, the controller 310 establishesa wireless connection to sensor 396 according to the wireless connectioninformation of sensor 396 or connection information 371.

In one embodiment, sensor 396 requires a physical connection at servicepoint 361 in order to be operated. Sensor service 376 includes thephysical connection information or a reference to connection information371 for the physical connection information to attach at service point361. Controller 310 instructs service rendering vehicle 601 to attachphysically at service point 361.

In one embodiment, sensor service 376 includes a sensor operation.Controller 310 retrieves sensor operation data 336 from materials 330corresponding to the sensor operation included in sensor service 376. Inone embodiment, sensor service 376 includes a sensor type, a brand name,a manufacturer identity, a make, a model number, a serial number or anidentity of sensor 396. Controller 310 uses sensor service 376 to selectand retrieve sensor operation data 336, which may include a dataconnection protocol, a piece of security data or key code to operatesensor 396, and an operation sequence or instructions corresponding tothe sensor type, the brand, manufacturer, make, model number, serialnumber or sensor identity. In one embodiment, sensor service 376includes one or more sensor operations such as to activate, de-activate,calibrate, adjust settings, configure a key code, or reset the sensor396. In one embodiment, sensor operation data 336 includes instructionsto turn arm 333, to generate and transmit data signals, to generateelectronic pulses, to establish data communication, or to transmitelectronic instructions to perform the necessary requested sensoroperation. In one embodiment, sensor operation data 336 includes a keycode to activate, de-activate, calibrate, change settings, configure orreset the sensor 396.

In one embodiment, sensor 396 includes a data store storing datacaptured by sensor 396. The captured data may include event log entries,usage data, security alerts, or other data relevant to sensor 396. Inone embodiment, sensor service 376 includes a data transfer operation toupload sensor 396 captured data. Controller 310 processes sensor service376 and transfers sensor 396 captured data into sensor operation data336.

FIG. 9 illustrates an exemplary embodiment of a process to render anelectric charging service. In one embodiment, controller 310 processescharging service 377 which indicates service object 360 includes anelectronic device 397. In one embodiment, charging service 377 indicateselectronic device 397 is wirelessly controlled. Charging service 377 mayinclude wireless connection information of electronic device 397 or areference to connection information 371 for a wireless connection withthe electronic device 397. The controller 310 instructs the servicerendering vehicle 601 to move within the proximity distance 610. Uponbeing informed that the service rendering vehicle 601 have moved withinthe proximity distance 610, the establishes the wireless connection withthe electronic device 397.

In one embodiment, electronic device 397 requires a physical connectionat service point 361 in order to be operated. Charging service 377includes the physical connection information or a reference toconnection information 371 for the physical connection information toattach at service point 361. Controller 310 instructs service renderingvehicle 601 to attach physically at service point 361.

In one embodiment, charging service 377 includes an electric chargingoperation. In one embodiment, charging service 377 includes an electriccurrent, a voltage, a battery type, a brand name, a manufactureridentity, a make, a model number, a serial number or an identity ofelectronic device 397. Controller 310 uses charging service 377 toselect a battery cell 337 from materials 330 where battery cell 337corresponds to the required electric current, the required voltage, thebrand name, manufacturer, make, model, serial number or electronicdevice 397 identity. In one embodiment, charging service 377 includesone or more electric charging operations such as to turn on, turn off,charge, or discharge.

In one embodiment, electronic device 397 includes a data store storingdata about electronic device 397. The data may include event logentries, usage data, security alerts, or other data relevant toelectronic device 397. In one embodiment, charging service 377 includesa data transfer operation to upload electronic device 397 data.Controller 310 processes charging service 377 and transfers electronicdevice 397 data into a storage connected to controller 310.

FIG. 10 illustrates an exemplary embodiment of a process to render aservice to a container. In one embodiment, controller 310 processescontainer service 378 which indicates service object 360 includes acontainer 398. In one embodiment, container service 378 requires aphysical connection at service point 361 in order to be operated.Container service 378 includes the physical connection information or areference to connection information 371 for the physical connectioninformation to attach at service point 361. Controller 310 instructsservice rendering vehicle 601 to attach physically at service point 361.

In one embodiment, container service 378 includes a container operation.In one embodiment, container service 378 includes a container type, abrand name, a manufacturer identity, a make, a model number, a serialnumber or an identity of container 398. Controller 310 uses containerservice 378 to select a container item 338 from materials 330 wherecontainer item 338 corresponds to the container type, the brand name,manufacturer, make, model, serial number or container 398 identity. Inone embodiment, container service 378 includes one or more containeroperations such as to refill, remove, replace, place a container item,or empty container 398. Controller 310 instructs arm 333 to actaccording to container service 378, for example, to refill container 398with container item 338, to remove container 398 and place container 398to an empty slot corresponding to container item 338, to replacecontainer 398 by container item 338, to place container item 338 ontocontainer 398, or to empty content of container 398 onto container item338.

In one embodiment, container 398 includes a data store storing dataabout container 398. The captured data may include event log entries,usage data, security alerts, or other data relevant to container 398. Inone embodiment, container service 378 includes a data transfer operationto upload container 398 captured data. Controller 310 processescontainer service 378 and transfers container 398 captured data into astorage connected to controller 310.

FIG. 11 illustrates an exemplary embodiment process to render a dynamiccomputing, service. In one embodiment, controller 310 processescomputing service 379 which includes one or more computing instructions379-1, and indicates service object 360 is to be serviced by applyingcomputing instructions 379-1. In one embodiment, computing service 379indicates service object 360 is wirelessly connected. Computing service379 may include wireless connection information of service object 360 ora reference to connection information 371 for a wireless connection withthe service object 360. The controller 310 instructs the servicerendering vehicle 601 to move within the area 610. Upon being informedthat the service rendering vehicle 601 have moved within the area 610,the establishes the wireless connection with the service object 360.

In one embodiment, service object 360 requires a physical connection atservice point 361 in order to be operated. Computing service 379includes the physical connection information or a reference toconnection information 371 for the physical connection information toattach at service point 361. Controller 310 instructs service renderingvehicle 601 to attach physically at service point 361.

In one embodiment, upon establishing a data communication connectionwith service object 360, controller 310 executes computing instructions379-1. In one embodiment, computing instructions 379-1 uses one or morecomputing programming, languages such as scripting languages Javascript,Python, Ruby, Perl; marked-up languages such as XML, JSON, HTML5;programming languages such as Java, C, C++; application programminginterfaces (API); or other computing languages. In one embodiment,controller 310 determines computing instructions 379-1 to require data,which may include other computing instructions, stored in storage 339 ofmaterials 330. Controller 310 selects storage 339 using computingservice 379 and uses storage 339 while applying computing instructions379-1. In one embodiment, controller 310 connects to a data network 500according to computing instructions 379-1 to establish a data connectionvia data network 500 to a network computing device. In one embodiment,computing instructions 379-1 includes instructions to operate arm 333and/or service rendering vehicle 601.

The present invention can take the form of an entirely hardwareembodiment, an entirely software embodiment or an embodiment containingboth hardware and software elements. In a preferred embodiment, thepresent invention is implemented in software, which includes but is notlimited to firmware, resident software, microcode, etc.

Furthermore, the present invention can take the form of a computerprogram product accessible from a computer usable or computer readablestorage medium providing program code for use by or in connection with acomputer or any instruction execution system. For the purposes of thisdescription, a computer usable or computer readable storage medium canbe any apparatus that can contain, store, communicate, propagate, ortransport the program for use by or in connection with the instructionexecution system, apparatus, or device. The medium can be an electronic,magnetic, optical, electromagnetic, infrared, or semiconductor system(or apparatus or device) or a propagation medium. Examples of acomputer-readable medium include a semiconductor or solid state memory,magnetic tape, a removable computer diskette, a random access memory(RAM), a read-only memory (ROM), a rigid magnetic disk and an opticaldisk. Current examples of optical disks include compact disk-read onlymemory (CD-ROM), compact disk-read/write (CD-R/W) and DVD. A computerreadable storage medium, as used herein, is not to be construed as beingtransitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

A data processing system suitable for storing and/or executing programcode will include at least one processor coupled directly or indirectlyto memory elements through a system bus. The memory elements can includelocal memory employed during actual execution of the program code, bulkstorage, and cache memories which provide temporary storage of at leastsome program code in order to reduce the number of times code must beretrieved from bulk storage during execution.

Input/output or I/O devices (including but not limited to keyboards,displays, point devices, etc.) can be coupled to the system eitherdirectly or through intervening I/O controllers.

Network adapters may also be coupled to the system to enable the dataprocessing system to become coupled to other data processing systems orremote printers or storage devices through intervening private or publicnetworks. Modems, cable modem and Ethernet cards are just a few of thecurrently available types of network adapters.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified local function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the invention. Asused herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof.

Although the present invention has been described in accordance with theembodiments shown, one of ordinary skill in the art will readilyrecognize that there could be variations to the embodiments and thosevariations would be within the spirit and scope of the presentinvention. Accordingly, many modifications may be made by one ofordinary skill in the art without departing from the spirit and scope ofthe appended claims.

What is claimed is:
 1. A method for charging an electric device by aservice rendering system, comprising: (a) receiving, by a controller ofthe service rendering system, an image captured by an image sensor; (b)processing, by the controller, the image to identify a label in theimage as corresponding to the electric device; (c) obtaining, by thecontroller, a service point location encoded in the label, wherein theservice point location comprises a location relative to a location ofthe label; (d) obtaining, by the controller, service informationcomprised in the label, the service information comprising a chargingservice, the charging service comprising a description of an electriccharging input of the electric device; (e) calculating, by thecontroller, a label position of the label using the image of the label;and (f) calculating, by the controller, a service point position usingthe service point location and the label position, wherein the servicepoint position comprises the electric charging input.
 2. The method ofclaim 1, further comprising: (g) issuing, by the controller,instructions to move the service rendering system to the electriccharging input at the service point position; and (h) connecting, by thecontroller, the service rendering system to the electric charging inputusing the description of the electric charging input, to perform one ormore electric charging operations.
 3. The method of claim 2, wherein theservice point comprises a wireless charging input, wherein the chargingservice further comprises wireless connection information and aproximity distance, wherein the issuing (g) and the connecting (h)comprises: (g1) issuing, by the controller, instructions to move theservice rendering system within the proximity distance of the servicepoint position; and (h1) establishing, by the controller, a wirelessconnection between the service rendering system and the electriccharging input using the wireless connection information.
 4. The methodof claim 3, wherein the service rendering system comprises an arm,wherein the issuing (g1) and the establishing (h1) comprises: (g1i)issuing, by the controller, instructions to move the arm of the servicerendering system within the proximity distance of the service pointposition; and (h1i) establishing, by the controller, the wirelessconnection between the arm and the electric charging input using thewireless connection information.
 5. The method of claim 2, wherein theservice point comprises a physical charging input, wherein the chargingservice further comprises physical connection information, wherein theconnecting (h) comprises: (h1) issuing, by the controller, instructionsto the service rendering system to physically attach to the electriccharging input using the physical connection information.
 6. The methodof claim 5, wherein the service rendering system comprises an arm,wherein the issuing (h1) comprises: (h1i) establishing, by thecontroller, the physical connection between the arm and the electriccharging input using the physical connection information.
 7. The methodof claim 2, wherein the charging service further comprises batteryinformation, wherein the method further comprises: (i) selecting, by thecontroller, a battery cell corresponding to the battery information, tobe used for the one or more charging operations.
 8. The method of claim7, wherein the electric device comprises a container, wherein theservice information further comprise a container service, wherein thecontainer service comprises container information, wherein the methodfurther comprises: (j) placing, by the service rendering system, thebattery cell into the container using the container information.
 9. Themethod of claim 2, wherein the service information further comprises anindication that access to the electric device requires authentication,wherein the connecting (h) comprises: (h1) connecting, by thecontroller, the service rendering system to the electric charging inputusing the description of the electric charging input; (h2) obtaining, bythe controller, connection security data for the electric device; and(h3) upon determining that the service rendering system is authenticatedby the electric device using the connection security data, issuing, bythe controller, instructions to the service rendering system to performthe one or more electric charging operations.
 10. The method of claim 9,wherein the connection security data comprises a security key, apasscode, a pin code, an answer to a question, or an authorized code.11. A non-transitory computer readable medium comprising computerreadable program code embodied therein for charging an electric deviceby a service rendering system, wherein when executed by a processor ofthe service rendering system, causes the processor to: (a) receive animage captured by an image sensor; (b) process the image to identify alabel in the image as corresponding to the electric device; (c) obtain aservice point location encoded in the label, wherein the service pointlocation comprises a location relative to a location of the label; (d)obtain service information comprised in the label, the serviceinformation comprising a charging service, the charging servicecomprising a description of an electric charging input of the electricdevice; (e) calculate a label position of the label using the image ofthe label; and (f) calculate a service point position using the servicepoint location and the label position, wherein the service pointposition comprises the electric charging input.
 12. The medium of claim11, wherein the processor is further caused to: (g) issue instructionsto move the service rendering system to the electric charging input atthe service point position; and (h) connect the service rendering systemto the electric charging input using the description of the electriccharging, input, to perform one or more electric charging operations.13. The medium of claim 12, wherein the service point comprises awireless charging input, wherein the charging service further compriseswireless connection information and a proximity distance, wherein theissue (h) and the connect (i) comprises: (g1) issue instructions to movethe service rendering system within the proximity distance of theservice point position; and (h1) establish a wireless connection betweenthe service rendering system and the electric charging input using thewireless connection information.
 14. The medium of claim 13, wherein theservice rendering system comprises an arm, wherein the issue (g1) andthe establish (h1) comprises: (g1i) issue instructions to move the armof the service rendering system within the proximity distance of theservice point position; and (h1i) establish the wireless connectionbetween the arm and the electric charging input using the wirelessconnection information.
 15. The medium of claim 12, wherein the servicepoint comprises a physical charging input, wherein the charging servicefurther comprises physical connection information, wherein the connect(h) comprises: (h1) issue instructions to the service rendering systemto physically attach to the electric charging input using the physicalconnection information.
 16. The medium of claim 15, wherein the servicerendering system comprises an arm, wherein the issue (h1) comprises:(h1i) establish the physical connection between the arm and the electriccharging input using the physical connection information.
 17. The mediumof claim 12, wherein the charging service further comprises batteryinformation, wherein the processor is, further caused to: (i) select abattery cell corresponding to the battery information, to be used forthe one or more charging operations.
 18. The medium of claim 17, whereinthe electric device comprises a container, wherein the serviceinformation further comprise a container service, wherein the containerservice comprises container information, wherein the processor isfurther caused to: (j) place the battery cell into the container usingthe container information.
 19. The medium of claim 12, wherein theservice information further comprises an indication that access to theelectric device requires authentication, wherein the connect (h)comprises: (h1) connect the service rendering system to the electriccharging input using the description of the electric charging input;(h2) obtain connection security data for the electric device; and (h3)upon determining that the service rendering system is authenticated bythe electric device using the connection security data, issueinstructions to the service rendering system to perform the one or moreelectric charging operations.
 20. The medium of claim 19, wherein theconnection security data comprises a security key, a passcode, a pincode, an answer to a question, or an authorized code.
 21. A servicerendering system, comprising: a controller; an image sensor coupled tothe controller; and a non-transitory computer readable medium comprisingcomputer readable program code embodied therein for charging an electricdevice, wherein when executed by controller, causes the controller to:(a) receive an image captured by the image sensor; (b) process the imageto identify a label in the image as corresponding to the electricdevice; (c) obtain a service point location encoded in the label,wherein the service point location comprises a location relative to alocation of the label; (d) obtain service information comprised in thelabel, the service information comprising a charging service, thecharging service comprising a description of an electric charging inputof the electric device; (e) calculate a label position of the labelusing the image of the label; and (f) calculate a service point positionusing the service point location and the label position, wherein theservice point position comprises the electric charging input.
 22. Thesystem of claim 21, wherein the controller is further caused to: (g)issue instructions to move the service rendering system to the electriccharging input at the service point position; and (h) connect theservice rendering system to the electric charging input using thedescription of the electric charging input, to perform one or moreelectric charging operations.
 23. The system of claim 22, wherein theservice point comprises a wireless charging input, wherein the chargingservice further comprises wireless connection information and aproximity distance, wherein the issue (h) and the connect (i) comprises:(g1) issue instructions to move the service rendering system within theproximity distance of the service point position; and (h1) establish awireless connection between the service rendering system and theelectric charging input using the wireless connection information. 24.The system of claim 23, wherein the service rendering system furthercomprises an arm, wherein the issue (g1) and the establish (h1)comprises: (g1i) issue instructions to move the arm of the servicerendering system within the proximity distance of the service pointposition; and (h1i) establish the wireless connection between the armand the electric charging input using the wireless connectioninformation.
 25. The system of claim 22, wherein the service pointcomprises a physical charging input, wherein the charging servicefurther comprises physical connection information, wherein the connect(h) comprises: (h1) issue instructions to the service rendering systemto physically attach to the electric charging input using the physicalconnection information.
 26. The system of claim 25, wherein the servicerendering system further comprises an arm, wherein the issue (h1)comprises: (h1i) establish the physical connection between the arm andthe electric charging input using the physical connection information.27. The system of claim 22, wherein the charging, service furthercomprises battery information, wherein the controller is further causedto: (i) select a battery cell corresponding to the battery information,to be used for the one or more charging operations.
 28. The system ofclaim 27, wherein the electric device comprises a container, wherein theservice information further comprise a container service, wherein thecontainer service comprises container information, wherein thecontroller is further caused to: (j) place the battery cell into thecontainer using the container information.
 29. The system of claim 22,wherein the service information further comprises an indication thataccess to the electric device requires authentication, wherein theconnect (h) comprises: (h1) connect the service rendering system to theelectric charging input using the description of the electric charginginput; (h2) obtain connection security data for the electric device; and(h3) upon determining that the service rendering system is authenticatedby the electric device using the connection security data, issueinstructions to the service rendering system to perform the one or moreelectric charging operations.
 30. The system of claim 29, wherein theconnection security data comprises a security key, a passcode, a pincode, an answer to a question, or an authorized code.